Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊
This playbook is triggered via HTTP request and is designed to be used as a sub-playbook by other Censys playbooks (CensysIncidentEnrichment, CensysEntityEnrichmentHost, CensysEntityEnrichmentCertificate, CensysEntityEnrichmentWebProperty, CensysAlertEnrichment). It receives enrichment data (host, web_property, certificate) along with the incident ARM ID and parent playbook name. The playbook processes each data type, extracts relevant fields (IP, autonomous system, WHOIS, location, DNS, service
| Attribute | Value |
|---|---|
| Type | Playbook |
| Solution | Censys |
| Source | View on GitHub |
This playbook uses 2 Logic App connectors / built-in actions:
| Connector / Action | Type | Connections | Actions |
|---|---|---|---|
azureloganalyticsdatacollector |
Managed | 1 | 3 |
azuresentinel |
Managed | 1 | 8 |
azureloganalyticsdatacollector (Managed)| Action | Method | Endpoint | Other |
|---|---|---|---|
| Send_Each_Host_Data | post | /api/logs |
— |
| Send_Web_Property_Data | post | /api/logs |
— |
| Send_certificate_data | post | /api/logs |
— |
azuresentinel (Managed)| Action | Method | Endpoint | Other |
|---|---|---|---|
| Add_comment_to_incident_(V3)_3 | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_1 | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_2 | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_5 | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_6 | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_7 | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3)_8 | post | /Incidents/Comment |
— |
| Add_comment_to_incident_(V3) | post | /Incidents/Comment |
— |
📄 Source: CensysAddIncidentComment/readme.md
This playbook is triggered via HTTP request and is designed to be used as a sub-playbook by other Censys playbooks (CensysIncidentEnrichment, CensysEntityEnrichmentHost, CensysEntityEnrichmentCertificate, CensysEntityEnrichmentWebProperty, CensysAlertEnrichment). It receives enrichment data (host, web_property, certificate) along with the incident ARM ID and parent playbook name. The playbook processes each data type, extracts relevant fields (IP, autonomous system, WHOIS, location, DNS, services, threats, vulnerabilities, labels, software), formats them into HTML tables, and adds them as comments to the Microsoft Sentinel incident. It handles comment character limits (splitting into multiple comments if needed) and enforces a maximum of 100 comments per incident. The enrichment data is also ingested into Azure Log Analytics custom tables (Incident_Enrich_Host_Data_CL, Incident_Enrich_WebProperty_Data_CL, Incident_Enrich_Certificate_Data_CL) for historical analysis. The playbook includes comprehensive error handling and returns appropriate HTTP responses.
Host comments additionally render the Censys reputation (label, score, class probabilities and top signals) and, when present in the payload, the GreyNoise, IPinfo (network and privacy) and Mallory data returned by the Censys Host Enrichment API, each as its own HTML table. Sections are only added when the corresponding data exists, so hosts retrieved from the standard host API render exactly as before. The calling playbook's name is passed in the parent_playbook field (set dynamically from workflow()['name'] by the parent playbooks).
Once deployment is complete, authorize each connection.
Configure the parent playbooks to call this sub-playbook using its HTTP trigger URL.
Ensure the playbook has appropriate permissions to add comments to incidents.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊